Skip to content

docs: add notes of v1.1.0 - #69

Merged
uniqueg merged 1 commit into
mainfrom
docs/68-notes-v1.1.0
Nov 9, 2026
Merged

uniqueg merged 1 commit into
mainfrom
docs/68-notes-v1.1.0

Conversation

@uniqueg

@uniqueg uniqueg commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Summary

Release preparation for v1.1.0 (RELEASING.md, step 2): adds the curated notes docs/releases/v1.1.0.md, drafted with release.sh draft v1.1.0 v1.0.0 origin/main and edited (intro naming the new action publish-release; TODO line removed). v1.1.0 is a minor step: since v1.0.0 the only change to actions/ is a new action (feat, #67).

Closes #68

Verification

  • bash .github/scripts/release.sh lint v1.1.0 docs/releases/v1.1.0.md: passes.
  • bash .github/scripts/release.sh check v1.1.0 origin/main: passes, previous=v1.0.0 (v1.1.0 is allowed).
  • pre-commit run --files docs/releases/v1.1.0.md: passes (markdownlint).
  • CI: passes (Lint, Test, CodeQL, CI passed).

Lane

Light lane: docs only (release notes), no code, CI, permissions or workflow changes; diff reviewed by hand.

🤖 Generated with Claude Code

Summary by Sourcery

Documentation:

  • Add curated v1.1.0 release notes documenting the new shared publish-release action and other changes since v1.0.0.

Add the curated notes of v1.1.0 (docs/releases/v1.1.0.md), drafted
with release.sh draft from the commits since v1.0.0 and edited; the
release adds the action publish-release.

Closes #68

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sourcery-ai

sourcery-ai Bot commented Nov 9, 2026

Copy link
Copy Markdown

Reviewer's Guide

Documentation

Add curated v1.1.0 release notes describing the new publish-release action and other changes since v1.0.0.

  • docs/releases/v1.1.0.md L1-35

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@uniqueg
uniqueg marked this pull request as ready for review November 9, 2026 14:37
@uniqueg
uniqueg merged commit 31f22fc into main Nov 9, 2026
7 checks passed
@uniqueg
uniqueg deleted the docs/68-notes-v1.1.0 branch November 9, 2026 14:38

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Linked issues

#68 chore: release v1.1.0 · 1 of 2 met · 1 to check by hand

# Requirement Status Notes
1 Add the curated notes at docs/releases/v1.1.0.md. ✅ Met The file contains the v1.1.0 intro and grouped release-note sections.
2 Tag the merged commit and approve Publish release so callers can pin the new action to the v1.1.0 release. 👀 Check by hand (manual process) After the notes PR is merged, the maintainer must push a signed, annotated tag for the merged commit and approve the Publish release job.

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: release v1.1.0

1 participant